Please add test strings in Tests step for easier test. Example: #573.

Please add test strings in Tests step for easier test. Example: #573.

Thanks, addressed by 7992a00

Like this:

Add some more test cases with no line break, multiple line breaks, with/without space
i.e.

message1```code```message2

message1 ``` code ``` message2

message1
```code```
message2

message1
``` code ```
message2


message1
```

code
```
message2


message1
```

code

```
message2


message1
```


code

```
message2


message1
```

code


```
message2

@0xmiroslav Do I need to add those cases to the unit testing or to the test strings in the PR description?

@0xmiroslav Do I need to add those cases to the unit testing or to the test strings in the PR description?

Both

@0xmiroslav can you please do the review checklist on this one?

Thanks!

@0xmiroslav After this PR is merged, do I need to create another PR in the App to update the expensify-common package version? What will be measured as the days for the PR merged - this PR or another PR for App?
Upwork contract says that if I can get merged within 3 days, I can get 50% bonus, but if merged after 9 days, I will get penalty

Just to confirm that this is not bug.

message1```code```message2

In edit mode:

message1```
code
```
message2

@0xmiroslav Yes, we can see the same result in the current staging environment.
I assume if we want to fix it, we will need to create another issue and address it, but as we don't really want the edit mode to be exactly as the original text, it can be decided by the product team.

Screenshots/Videos

@danieldoglas Is there anything I need to do to merge this PR?

@danieldoglas Can you please update the version of expensify-common?

@nikosamofa You just need to follow this: https://github.com/Expensify/expensify-common?tab=readme-ov-file#deploying-a-change-expensify-only on the app repo!